Server device, information processing method, program, and storage medium

ABSTRACT

The above server device receives acquired information acquired by the vehicle from an onboard terminal mounted on the vehicle during a use of the vehicle by a user, and stores the acquired information. Then, the server device provides information requested by a service providing company which provides a service related to the vehicle, among the required information, to a server device of the service providing company. Also, the server device deletes the acquired information stored in the storage unit when it receives the deletion request of the acquired information, and transmits a deletion request of the acquired information provided o the service providing company to the server device of the service providing company based on the deletion request.

TECHNICAL FIELD

The present invention relates to techniques for providing variousservices with respect to autonomous driving vehicles used forcar-sharing.

BACKGROUND TECHNIQUE

When autonomous driving vehicles become popular, it is thought that, notonly an autonomous driving vehicle is owned as a private car, but carsharing will develop. Techniques relating to car sharing of autonomousdriving vehicles are described in Patent reference 1.

PRIOR ART REFERENCES Patent Reference

-   -   Patent Reference 1: Japanese Patent Application Laid-Open under        No. 2016-57946.

SUMMARY OF THE INVENTION Problem to be Solved by the Invention

An autonomous driving vehicle transmits various information such as theposition and route in which the vehicle is traveling, information ofobjects in the vicinity detected by the sensor or else to a server whichmanages the autonomous driving vehicles. Then, companies providingvarious services related to autonomous driving vehicles require variousinformation related to the autonomous driving vehicles to provideservices. Now, it is considered a case where a user receives servicesrelated to an autonomous vehicle, for example services by an insurancecompany. In this case, it is desirable that the server that manages theautonomous driving vehicle provides only the information required by theinsurance company among the information obtained from the autonomousdriving vehicle to the insurance company. Therefore, there is a need fora system in which the servers that manage the autonomous drivingvehicles select information obtained from autonomous driving vehicles,and provide the information to the companies that provide the services.

The present invention has been made to solve the problems as describedabove, and an object thereof is to provide various services for anautonomous driving vehicle for car-sharing.

Means for Solving the Problem

An invention described in claims is a server device which collectsinformation from a vehicle, comprising: a storage unit configured toreceive acquired information acquired by the vehicle from an onboardterminal mounted on the vehicle during a use of the vehicle by a user,and stores the acquired information; an information providing unitconfigured to provide information requested by a service providingcompany which provides a service related to the vehicle, among therequired information, to a server device of the service providingcompany; a reception unit configured to receive a deletion request ofthe acquired information; a deletion unit configured to delete theacquired information stored in the storage unit; and a transmission unitconfigured to transmit a deletion request of the acquired informationprovided to the service providing company to the server device of theservice providing company based on the deletion request.

Another invention described in claims is an information processingmethod executed by a server device which collects information from avehicle, comprising: a storage process configured to receive acquiredinformation acquired by the vehicle from an onboard terminal mounted onthe vehicle during a use of the vehicle by a user, and stores theacquired information in a storage unit; an information providing processconfigured to provide information requested by a service providingcompany which provides a service related to the vehicle, among therequired information, to a server device of the service providingcompany; a reception process configured to receive a deletion request ofthe acquired information; a deletion process configured to delete theacquired information stored in the storage unit; and a transmissionprocess configured to transmit a deletion request of the acquiredinformation provided to the service providing company to the serverdevice of the service providing company based on the deletion request.

Still another invention described in claims is a program executed by aserver device which includes a computer and which collects informationfrom a vehicle, the program causing the computer to function as: astorage unit configured to receive acquired information acquired by thevehicle from an onboard terminal mounted on the vehicle during a use ofthe vehicle by a user, and stores the acquired information; aninformation providing unit configured to provide information requestedby a service providing company which provides a service related to thevehicle, among the required information, to a server device of theservice providing company; a reception unit configured to receive adeletion request of the acquired information; a deletion unit configuredto delete the acquired information stored in the storage unit; and atransmission unit configured to transmit a deletion request of theacquired information provided to the service providing company to theserver device of the service providing company based on the deletionrequest.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic configuration of a car sharing system according toan embodiment.

FIG. 2 is a block diagram illustrating an internal configuration of auser terminal.

FIG. 3 is a block diagram illustrating an internal configuration of anonboard terminal.

FIG. 4A is a block diagram illustrating an internal configuration of thevehicle cloud server.

FIG. 4B is a block diagram illustrating an internal configuration of aservice cloud server.

FIG. 5 is an example of service information.

FIG. 6 is a flowchart of service information registration processing.

FIGS. 7A and 7B are examples of service information transmitted from theonboard terminal to the vehicle cloud.

FIG. 8 is a flowchart of a first example of use start processing.

FIG. 9 is a flowchart of a second example of the use start processing.

FIG. 10 is a flowchart of information providing processing to theservice cloud server.

FIG. 11 is a flowchart of use end processing of the shared vehicle.

FIG. 12 is a flowchart of history deletion processing.

FIG. 13 is schematically illustrates an authentication method usingbiometric information.

FIG. 14 is a flowchart illustrating authentication processing at thetime of starting the use using the biometric information.

FIG. 15 is a flowchart of the authentication processing during the useof the shared vehicle.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

According to one aspect of the present invention, there is provided aserver device which collects information from a vehicle, comprising: astorage unit configured to receive acquired information acquired by thevehicle from an onboard terminal mounted on the vehicle during a use ofthe vehicle by a user, and stores the acquired information; aninformation providing unit configured to provide information requestedby a service providing company which provides a service related to thevehicle, among the required information, to a server device of theservice providing company; a reception unit configured to receive adeletion request of the acquired information; a deletion unit configuredto delete the acquired information stored in the storage unit; and atransmission unit configured to transmit a deletion request of theacquired information provided to the service providing company to theserver device of the service providing company based on the deletionrequest.

The above server device receives acquired information acquired by thevehicle from an onboard terminal mounted on the vehicle during a use ofthe vehicle by a user, and stores the acquired information. Then, theserver device provides information requested by a service providingcompany which provides a service related to the vehicle, among therequired information, to a server device of the service providingcompany. Also, the server device deletes the acquired information storedin the storage unit when it receives the deletion request of theacquired information, and transmits a deletion request of the acquiredinformation provided to the service providing company to the serverdevice of the service providing company based on the deletion request.

In one mode of the above server device, the storage unit storesinformation requested by the service providing company for each serviceproviding company.

In a preferred example, the reception unit receives the deletion requestfrom the onboard terminal. In another preferred example, the receptionunit receives the deletion request from a terminal device of the user.

Another mode of the above server device further comprises a notificationunit configured to receive a notification indicating that the acquiredinformation is deleted from the server device of the service providingcompany, and notifies the onboard terminal that the acquired informationis deleted from the server device of the service providing company.Thus, it is possible to notify the user that the acquired information isdeleted from the server device of the service providing company.

In still another mode of the above server device, the notification unitcompares an amount of the acquired information provided to the serviceproviding company with the amount of the acquired information deleted bythe service providing company to confirm that the acquired informationis deleted, and notifies the onboard terminal that the acquiredinformation is deleted from the server device of the service providingcompany when it is confirmed that the acquired information is deleted.

In still another mode of the above server device, the notification unitnotifies the onboard terminal that the acquired information is deletedfrom the storage unit by the deletion unit. Thus, it is possible tonotify the user that the acquired information is deleted from thestorage unit of the server device.

According to another aspect of the present invention, there is providedan information processing method executed by a server device whichcollects information from a vehicle, comprising: a storage processconfigured to receive acquired information acquired by the vehicle froman onboard terminal mounted on the vehicle during a use of the vehicleby a user, and stores the acquired information in a storage unit; aninformation providing process configured to provide informationrequested by a service providing company which provides a servicerelated to the vehicle, among the required information, to a serverdevice of the service providing company; a reception process configuredto receive a deletion request of the acquired information; a deletionprocess configured to delete the acquired information stored in thestorage unit; and a transmission process configured to transmit adeletion request of the acquired information provided to the serviceproviding company to the server device of the service providing companybased on the deletion request. Thus, the information acquired during theuse of the vehicle is deleted in response to the user's deletionrequest.

According to still another aspect of the present invention, there isprovided a program executed by a server device which includes a computerand which collects information from a vehicle, the program causing thecomputer to function as: a storage unit configured to receive acquiredinformation acquired by the vehicle from an onboard terminal mounted onthe vehicle during a use of the vehicle by a user, and stores theacquired information; an information providing unit configured toprovide information requested by a service providing company whichprovides a service related to the vehicle, among the requiredinformation, to a server device of the service providing company; areception unit configured to receive a deletion request of the acquiredinformation; a deletion unit configured to delete the acquiredinformation stored in the storage unit; and a transmission unitconfigured to transmit a deletion request of the acquired informationprovided to the service providing company to the server device of theservice providing company based on the deletion request. By executingthis program by the computer, the above server device may be realized.This program may be handled in a manner stored in a storage medium.

EMBODIMENTS

Preferred embodiments of the present invention will be described belowwith reference to the accompanied drawings.

[Car Sharing System] (Overall Configuration)

FIG. 1 illustrates a schematic configuration of a car sharing systemaccording to an embodiment. The car sharing system includes a userterminal 10 used by a user, a shared vehicle V. a vehicle cloud server30, and a service cloud server 40.

The user terminal 10 is a terminal device used by a user using a sharedvehicle, and is typically a smart phone of the user or the like. Theshared vehicle V is an autonomous driving vehicle provided to users. Anonboard terminal 20 is mounted on the shared vehicle V, and the userterminal 10 and the onboard terminal 20 is capable of transmitting andreceiving data by wireless communication.

The vehicle cloud server 30 is a server device constituting the vehiclecloud. The vehicle cloud is a cloud operated by an informationcollection company that manages autonomous driving vehicles provided tousers, and collects various types of information from the autonomousdriving vehicles. The information collection companies are operated bymanufacturers of the autonomous driving vehicles. For example, if thereare three companies A, B and C as the automobile manufacturers of theautonomous driving vehicles, an information collection company operatedby A, an information collection company operated by B and an informationcollection company operated by C exist individually, and eachinformation collection company collects various types of informationfrom the autonomous driving vehicles manufactured by the automobilemanufacturer that operates the information collection company.

The service cloud server 40 is a server device constituting a servicecloud. The service cloud is a cloud operated by a service providingcompany that provides services related to autonomous driving vehicles.The service providing companies include an insurance company thatprovides services related to insurance, a map service company thatprovides services related to maps, a parking lot service company thatprovides services related to parking lots, and a route search servicecompany that provides services related to route search.

The onboard terminal 20 mounted on the shared vehicle V, the vehiclecloud server 30 and the service cloud server 40 can communicate wiredlyor wirelessly through the network 5.

(User Terminal)

Next, the user terminal will be described in detail. FIG. 2 is a blockdiagram illustrating the internal configuration of the user terminal 10.The user terminal 10 includes a communication unit 11, a storage unit12, a control unit 13, a display unit 14 and an input unit 15. Thesecomponents can communicate with each other through a bus line 19.

The communication unit 11 communicates with the external world bywireless communication. In this embodiment, the communication unit 11mainly performs wireless communication with the onboard terminal 20 ofthe shared vehicle V. The storage unit 12 includes a ROM, a RAM, a flashmemory and the like, and stores programs for various kinds of processingexecuted by the user terminal 10. The storage unit 12 is also used as awork memory when various kinds of processing are executed. Further, thestorage unit 12 stores service information described later.

The control unit 13 is composed of a computer such as a CPU, andcontrols the entire user terminal 10. Specifically, the control unit 13performs various processing by executing various programs stored in thestorage unit 12. The display unit 14 is a liquid crystal display or thelike, and displays various information. The input unit 15 is a touchpanel or the like provided on the display unit 14, and is used when theuser performs an instruction input.

(Onboard Terminal)

Next, the onboard terminal 20 will be described in detail. FIG. 3 is ablock diagram illustrating the internal configuration of the onboardterminal 20. As illustrated, the onboard terminal 20 mainly includes acommunication unit 21, a storage unit 22, an input unit 23, a controlunit 24, an interface 25 and an output unit 26. Each element in theonboard terminal 20 is connected to each other via a bus line 29.Further, the interface 25 is connected to the sensor unit 27.

Based on the control of the control unit 24, the communication unit 21transmits various kinds of information acquired by the shared vehicle V(hereinafter, also referred to as “upload data”) to the vehicle cloudserver 30, and receives map data for updating the map DB from thevehicle cloud server 30. The communication unit 21 communicates with theuser terminal through wireless communication. Furthermore, thecommunication unit 21 may perform processing of transmitting a signalfor controlling the vehicle to the vehicle, and processing of receivinga signal relating to the state of the vehicle from the vehicle.

The storage unit 22 stores programs executed by the control unit 24, andinformation necessary for the control unit 24 to execute predeterminedprocessing. In this embodiment, the storage unit 22 stores a pluralityof map DBs, sensor data cache and vehicle attribute information.

The map DB is a database including, for example, road data, facilitydata and ground feature data around the road. The road data include lanenetwork data for route search, road shape data, traffic regulation data,etc. The ground feature data include information of signboards such asroad signs, road marks such as stop lines, road division lines such ascenter lines and structures along roads. Further, the ground featuredata may include high-precision point group information of the groundfeature for use in the vehicle position estimation. In addition, variousdata necessary for position estimation may be stored in the map DB.

The sensor data cache is a cache memory for temporarily holding theoutput data of the sensor unit 27. Vehicle attribute informationindicate information about the attribute of the shared vehicle Vequipped with the onboard terminal 20, such as the type of vehicle, thevehicle ID, the vehicle size including the vehicle length, the vehiclewidth and the vehicle height, fuel type of the vehicle, etc.

The input unit 23 is a button, a touch panel, a remote controller, avoice input device or the like for the user's operation. For example,the input unit 23 receives an input for specifying a destination for theroute search or an input for specifying ON or OFF of the autonomousdriving, and supplies the generated input signal to the control unit 24.The output unit 26 is, for example, a display or a speaker or the likefor outputting information based on the control of the control unit 24.

The interface 25 performs an interface operation for supplying theoutput data of the sensor unit 27 to the control unit 24 and the sensordata cache. The sensor unit 27 includes a plurality of external sensorsfor recognizing the peripheral environment of the vehicle such as alidar and a camera, and internal sensors such as a GPS receiver, a gyrosensor, a position sensor, a 3-axis sensor. The lidar discretelymeasures the distance to an object existing in the external world,recognizes the surface of the object as a three-dimensional point group,and generates point group data. The camera generates image data takenfrom the vehicle. The position sensor is provided to detect the positionof each external sensor, and the three-axis sensor is provided to detectthe posture of each external sensor. The sensor unit 27 may include anexternal sensor and an internal sensor other than the external sensorsand the internal sensors shown in FIG. 3. For example, the sensor unit27 may include an ultrasonic sensor, an infrared sensor, a microphone orthe like as an external sensor.

The control unit 24 includes a CPU or the like for executingpredetermined programs on one or more platforms, and controls the entireonboard terminal 20. The control unit 24 functionally includes aposition estimation unit, an object detection unit and an upload datageneration unit.

The position estimating unit estimates the position of the own vehicle(including the attitude of the vehicle) based on the output data of thesensor unit 27 held in the sensor data cache and the map DB. Theposition estimating unit is capable of performing various positionestimation methods. The position estimating unit executes, for example,an own-vehicle position estimation method by dead reckoning (autonomousnavigation) based on the output of the autonomous positioning sensorsuch as a GPS receiver and a gyro sensor, an own-vehicle positionestimation method for further collating the road data of the map DB tothe autonomous navigation (map matching), an own-vehicle positionestimation method based on the output data of the external sensors suchas a lidar or a camera and the position information of the landmarkindicated by ground feature information of the map DB based on apredetermined object (landmark) existing in the surroundings. Then, theposition estimating unit executes the position estimation method thathas the highest estimation accuracy among the currently executableposition estimation methods, and supplies the vehicle positioninformation indicating the vehicle position obtained based on theexecuted position estimation method to the upload data generating unit.The position estimating unit includes information specifying theexecuted position estimation method in the own-vehicle positioninformation, and supplies the information to the upload data generatingunit.

The object detecting unit detects a predetermined object based on thepoint group information, the image data, the voice data and the likeoutput by the sensor unit 27. In this case, for example, the objectdetecting unit extracts the ground feature data corresponding to theobject detected by the sensor unit 27 from the map DB based on theown-vehicle position estimated by the position estimating unit. Whenthere is a difference between the position and the shape of the objectdetected by the sensor unit 27 and the position and the shape of theobject indicated by the ground feature data extracted from the map DB,or when there is no corresponding ground feature data in the map DB, theobject detection unit supplies information about the object detected bythe sensor unit 27 to the upload data generation unit.

The upload data generating unit generates the upload data based on theown-vehicle position information supplied from the position estimatingunit, the object data supplied from the object detecting unit and theoutput data of the sensor unit 27 supplied from the sensor data cache.Then, the upload data generating unit transmits the generated uploaddata to the vehicle cloud server

(Vehicle Cloud Server)

Next, the vehicle cloud server 30 will be described in detail. FIG. 4Ais a block diagram illustrating the internal configuration of thevehicle cloud server 30. As illustrated, the vehicle cloud server 30includes a communication unit 31, a storage unit 32, a control unit 33,a service information DB 34 and a history DB 35. The elements in thevehicle cloud server 30 are connected with each other via a bus line 39.

The communication unit 31 communicates with the onboard terminal 20 ofthe shared vehicle V and the service cloud server 40 based on thecontrol of the control unit 33. Specifically, the communication unit 31receives the upload data from the onboard terminal 20, and transmits theinformation corresponding to the provision information described laterto the service cloud server 40.

The storage unit 32 includes a ROM, a RAM and the like, and storesprograms for various kinds of processing executed by the vehicle cloudserver 30. The storage unit 32 is also used as a work memory whenvarious kinds of processing are executed.

The control unit 33 is composed of a computer such as a CPU, andcontrols the entire vehicle cloud server 30. Specifically, by executingvarious programs stored in the storage unit 32, the control unit 33performs various processing.

The service information DB 34 stores the service information transmittedfrom the onboard terminal 20. The service information will be describedlater in detail.

The history DB 35 stores the upload data acquired by the vehicle cloudserver 30 from the onboard terminal 20. Specifically, the history DB 35stores the information received from the onboard terminal 20 inassociation with the vehicle ID of the shared vehicle V mounting theonboard terminal 20 and the reception time. Further, the history DB 35may store the provision information that the vehicle cloud server 30transmitted to the service cloud server 40, as a history. In this case,in association with the provision information, information specifyingthe service cloud server 40 to which the provision information wastransmitted.

In the above configuration, the communication unit 31 is an example ofthe reception unit, the transmission unit and the notification unit ofthe present invention. The storage unit 32 is an example of the storageunit of the present invention, and the control unit 33 is an example ofthe information providing unit and the deletion unit of the presentinvention.

(Service Cloud Server)

Next, the service cloud server 40 will be described in detail. FIG. 4Bis a block diagram illustrating the internal configuration of theservice cloud server 40. As illustrated, the service cloud server 40includes a communication unit 41, a storage unit 42, a control unit 43,a contract information DB 44 and a history DB 45. The elements in theservice cloud server 40 are connected to each other via a bus line 49.

The communication unit 41 communicates with the vehicle cloud server 30under the control of the control unit 43. Specifically, thecommunication unit 41 receives information corresponding to theprovision information described later from the vehicle cloud server 30.

The storage unit 42 includes a ROM, a RAM and the like, and storesprograms for various kinds of processing executed by the service cloudserver 40. The storage unit 42 is also used as a work memory whenvarious kinds of processing are executed.

The control unit 43 is composed of a computer such as a CPU, andcontrols the entire service cloud server 40. Specifically, by executingvarious programs stored in the storage unit 42, the control unit 43performs various processing.

The contract information DB 44 stores the contract information. Thecontract information is information that specifies the service contentsprovided by the service providing company operating the service cloudserver 40 to the users using the shared vehicles V by the car sharingservice. For example, if the service providing company is an insurancecompany, the contract information includes the contents of the insurancecontract that the user has signed with the insurance company. Inaddition, the contract information includes the provision informationbased on the contract. That is, the contract information includes theinformation that the vehicle cloud server 30 should provide to theservice providing company based on the contract.

The history DB 45 stores information that the service cloud server 40acquired from the vehicle cloud server 30. This information isinformation transmitted from the vehicle cloud server 30 as theinformation corresponding to the provision information indicating theinformation requested by the service providing company, among theinformation that the vehicle cloud server 30 acquired from the onboardterminal 20. Specifically, the history DB 45 stores the informationreceived from the vehicle cloud server 30 in association with theinformation identifying the vehicle cloud server 30 that transmitted theinformation, a 2) reception time and the like.

[Service Information]

Next, the service information will be described. The service informationis the information related to the services that users using the sharedvehicle V have contracted with various service providing companies. Theservice information is stored in the storage unit 12 of the userterminal 10 as shown in FIG. 2.

FIG. 5 illustrates an example of the service information. Asillustrated, the service information includes a “shared vehicle userID,” “vehicle cloud,” “service cloud user ID,” “provision information,”and “destination address”.

The “shared vehicle user ID” is the ID of the user registered to theshared vehicle operation company. A shared vehicle operation company isa company that provides shared vehicle V to users. As mentioned above,the shared vehicle V is an autonomous driving vehicle manufactured bymultiple automobile manufacturers. The shared vehicle operation companyprepares the autonomous driving vehicles of those automobilemanufacturers by purchasing them, and provides them to the users. Atthis time, the user makes a user contract with the shared vehicleoperation company. The ID given to the user from the shared vehicleoperation company at that time is the shared vehicle user ID.

The “vehicle cloud” refers to the vehicle cloud with which the sharedvehicle operation company used by the users made contract. In thisembodiment, it is assumed that the shared vehicle operation company is acompany that provides the user with the shared vehicle V manufacturedand managed by the automobile manufacturers A and B. In this case, theshared vehicle operation company purchases the autonomous drivingvehicles of the automobile manufacturers A and B, and provides them tothe users as the car sharing service, for example. Also, the sharedvehicle operation company asks the information collection companyoperated by those automobile manufacturers to manage the shared vehicleV provided to the users. Therefore, the service information stored inthe user terminal 10 includes the information relating to the vehiclecloud operated by the automobile manufacturers A and B as theinformation collection company. In the example shown in FIG. 5, thevehicle cloud “CL001” operated by the automobile manufacturer A and thevehicle cloud “CL002” operated by the automobile manufacturer Barestored. When a shared vehicle operation company makes a contract with anew information collection company, that vehicle cloud will be added.

While the user is using the shared vehicle V provided by the sharedvehicle operation company, the onboard terminal 20 of the shared vehicleV transmits various information acquired during the traveling to thevehicle cloud server 30 as the upload data. For example, if the user isprovided with the shared vehicle V of the automobile manufacturer A fromthe shared vehicle operation company, the onboard terminal 20 of theshared vehicle V uploads the information obtained during the travelingto the vehicle cloud “CL001” of the information collection companyoperated by the automobile manufacturer A.

The “service cloud user ID” is the user ID for the service cloudoperated by the service providing company with which the user made acontact. The service cloud user ID is registered for each vehicle cloudoperated by an automobile manufacturer. In the example of FIG. 5, withrespect to the vehicle cloud CL001 operated by the automobilemanufacturer A, the user made contracts with an insurance company, a mapservice company, a parking lot service company and a route searchservice company. Therefore, when the user uses the shared vehicle V ofthe automobile manufacturer A, the user can receive the services by theinsurance company, the map service company, the parking lot servicecompany and the route search service company. Specifically, in theexample of FIG. 5, the service cloud user ID for the insurance companyis “XXXX1”, the service cloud user ID for the map service company is“ZZZZ1”, the service cloud user ID for the parking lot service companyis “WWWWW”, and the service cloud user ID for the route search servicecompany is “RRRRR”.

Similarly, with respect to vehicle cloud CL002 operated by theautomobile manufacturer B, the user made contracts with the insurancecompany and the map service company. Therefore, the users can receivethe services by the insurance company and the map service company whenusing the shared vehicle V of the automobile manufacturer B.Specifically, in the example of FIG. 5, the service cloud user ID forthe insurance company is “XXXX2” and the service cloud user ID for themap service company is “ZZZZ2.” In some cases, one service providingcompany provides the service to the user by using the service of anotherservice providing company. Specifically, in the case where the routesearch service company contracts with the map service company, the routesearch company can provide the user with the latest map and the routesearch service based on the latest map, thereby improving the servicelevel for the user. In this case, the route search service company mayreceive the service directly from the map service company to obtain thelatest map. Alternatively, the service cloud user ID of the map servicecompany may be supplied from the route search service company to theuser so that the user can directly receive the service from the mapservice company.

The “provision information” indicates the information to be provided toeach service cloud server 40, among various kinds of information thatthe vehicle cloud server 30 obtained from the onboard terminal 20. Forexample, in the example of FIG. 5, for the insurance company, “shootinginformation by the camera for N minutes before and after the occurrenceof the accident” is specified as the provision information. This isobtained by shooting the outside of the vehicle with an onboard camera,which is one of the sensors mounted on the shared vehicle V, and it isuseful information to clarify the situation at the time of the accidentand the cause of the accident. When an accident occurs to the sharedvehicle V, the service cloud server 30 transmits the shootinginformation by the camera for N minutes before and after the occurrenceof the accident among the information obtained from the onboard terminal20 of the shared vehicle V to the service cloud server 40 of theinsurance company. The insurance company can provide adequate insuranceservices based on the shooting information of the shared vehicle V.

Similarly, for the map service company, “recognized object information”and “travel route information” are defined as the provision information.Therefore, the service cloud server 30 transmits the recognized objectinformation and the travel route information among the informationacquired from the onboard terminal 20 of the shared vehicle V to theservice cloud server 40 of the map service company. The map servicecompany can update map data based on those information. Also, the mapservice company can provide the contracted users of the shared vehicle Vwith the service of supplying the latest maps with updated data.

For the parking lot service company, “user's destination” is set as theprovision information. Therefore, among the information obtained fromthe onboard terminal 20 of the shared vehicle V, the service cloudserver 30 transmits the destination set by the user to the service cloudserver 40 of the parking lot service company. The parking lot servicecompany notifies the terminal device 20 of a parking lot capable ofparking the shared vehicle V, among the parking lots in the vicinity ofthe destination, via the vehicle cloud server 30. Thus, the sharedvehicle V can be automatically parked in the parking lot near thedestination by autonomous driving.

For the route search service company, “startingpoint/destination/on-route point” and “traveling area” are set as theprovision information. Therefore, among the information acquired fromthe onboard terminal 20 of the shared vehicle V, the service cloudserver 30 transmits the “starting point/destination/on-route point” andthe “traveling area” set by the user to the service cloud server 40 ofthe route search service company. The route search service companynotifies the terminal device 20 of the travel route along the user'sdesire via the vehicle cloud server 30 based on the information of the“starting point/destination/on-route point” and the “traveling area”.Thus, the shared vehicle V can reach from the starting point to thedestination on an appropriate route by autonomous driving.

The “destination address” indicates the address to which the informationcorresponding to the provision information is transmitted, i.e., theaddress of the service cloud. In the example of FIG. 5, when an accidentoccurs to the shared vehicle V, the vehicle cloud server 30 transmitsthe shooting information by the camera for N minutes before and afterthe accident to the address “xxx.xxx.co.jp”.

[Registration Processing of Service Information]

Next, processing of registering the above-described service informationto the user terminal 10 and the onboard terminal 20 will be described.FIG. 6 is a flowchart of the service information registrationprocessing. First, after starting the application program in the userterminal 10, the user enters the shared vehicle user ID and the servicecloud user ID into the user terminal 10, and the user terminal 10receives them (Step S11). The shared vehicle user ID is the user IDassigned to the user by the shared vehicle operation company, and theservice cloud user ID is the user ID assigned to the user by eachservice providing company. If the user has made contracts with multipleservice providing companies, the user enters the service cloud user IDof each service providing company.

The user terminal 10 transmits the service cloud user ID received instep S11 to the service cloud server 40 operated by the correspondingservice providing company (step S12). The service cloud server 40 refersto the contract information DB 44, acquires the provision informationcorresponding to the user's contract (step S13), and transmits theprovision information to the user terminal 10 together with thedestination address of the service cloud server 40 (step S14).

As described above, the service providing company A having a contractwith the user (e.g., the route search service company) may provide aservice by utilizing the service of another service providing company B(e.g., the map service company). When the service providing company Aprovides the service cloud user ID of the service providing company B tothe user, it is preferred that the user ID of the service providingcompany B is transmitted from the service providing company A to theuser terminal 10 in step S13 and automatically registered to the userterminal 10. In this case, when the user ID of the service providingcompany B is registered, the user terminal 10 transmits the servicecloud user ID to the service cloud server 40 operated by the serviceproviding company B by the process in step 312. Alternatively, theservice cloud server 40 of the service providing company A may acquirethe provision information and the destination address from the servicecloud server 40 of the service providing company B, and transmit theinformation to the user terminal 10 together with the service cloud userID of the service providing company B to register the information.

The user terminal 10 stores the received provision information and thedestination address in the storage unit 12 as the service information inassociation with the service cloud user ID (step S15). Thus, the serviceinformation as shown in FIG. 5 is stored in the user terminal 10.

Thereafter, when the user uses the shared vehicle V, the serviceinformation is transmitted from the user terminal 10 to the onboardterminal 20 (step S16). For example, when the user operates the userterminal 10 or the onboard terminal 20, the communication between theuser terminal 10 and the onboard terminal 20 is established, and theservice information is transmitted from the user terminal 10 to theonboard terminal 20. When receiving the service information from theuser terminal 10, the onboard terminal 20 stores the service informationin the service information DB 34 and transmits the service informationto the vehicle cloud server 30 (step S17). In this case, the onboardterminal 20 transmits only a part of the information related to thevehicle cloud server 30 of the transmission destination among theservice information. For example, when the onboard terminal 20 receivesthe service information shown in FIG. 5 from the user terminal 10, theonboard terminal device 20 transmits only the part of the informationcorresponding to the vehicle cloud CL001 shown in FIG. 7A to the vehiclecloud server 30 of the vehicle cloud CL001, and transmits only the partof the information corresponding to the vehicle cloud CL002 shown inFIG. 7 B to the vehicle cloud server 30 of the vehicle cloud CL002.

[Use Start Processing]

Next, the processing by which the user starts using the shared vehicle Vwill be described.

First Example

In the first example, the service cloud server 40 authenticates the userbased on the service cloud user ID. FIG. 8 is a flowchart of a firstexample of the use start processing. As a premise, as shown in step S16of FIG. 6, it is assumed that the onboard terminal 20 has received andstored the service information from the user terminal 10.

First, when the user performs an instruction input to start the use ofthe shared vehicle V by operating the user terminal 10, the userterminal 10 transmits a use start request to the onboard terminal 20(step S20). The onboard terminal 20 acquires the shared vehicle user IDand the service cloud user ID associated with the vehicle cloud for theshared vehicle V by referring to the service information of the user,and transmits them to the vehicle cloud server 30 (step S21).

The vehicle cloud server 30 performs authentication based on the sharedvehicle user ID received from the onboard terminal 20 (step S22).Namely, the vehicle cloud server 30 determines whether the user has auser contract with the shared vehicle operation company. Upon successfulauthentication, the vehicle cloud server 30 transmits the service clouduser ID to the corresponding service cloud server 40 (step S23).Incidentally, when the authentication fails, the vehicle cloud server 30notifies the failure to the onboard terminal 20, and the processingends.

The service cloud server 40 performs authentication based on the servicecloud user ID received from the vehicle cloud server 30 (step S24).Specifically, the service cloud server 40 refers to the contractinformation DB 44, and determines whether or not a contractcorresponding to the service cloud user ID validly exists. Then, theservice cloud server 40 transmits the authentication result to thevehicle cloud server 30 (step S25).

The vehicle cloud server 30 transmits the authentication result receivedfrom the service cloud server 40 to the onboard terminal 20 (step S26).The onboard terminal 20 notifies the user of the authentication resultby display by the output unit 26 or the like. Thus, the processing ends.

Second Example

In the second example, the service cloud server 40 authenticates theuser based on the service cloud user ID and the vehicle information.FIG. 9 is a flowchart of a second example of the use start processing.As a premise, as shown in step S16 of FIG. 6, it is assumed that theonboard terminal 20 has received and stored the service information fromthe user terminal 10.

First, when the user performs an instruction input of starting the useby operating the user terminal 10, the user terminal 10 transmits a usestart request to the onboard terminal 20 (step S30). The onboardterminal 20 acquires the shared vehicle user ID and the service clouduser ID associated with the vehicle cloud for the shared vehicle V byreferring to the service information of the user, and transmits them tothe vehicle cloud server 30 together with the vehicle ID of the sharedvehicle V on which the onboard terminal 20 itself is mounted (step S31).

The vehicle cloud server 30 performs authentication based on the sharedvehicle user ID received from the onboard terminal 20 (step S32).Namely, the vehicle cloud server 30 determines whether or not the userhas a user contract with the shared vehicle operation company. When theauthentication is successful, the vehicle cloud server 30 acquires thevehicle information (e.g., information about the vehicle type of theshared vehicle v, the travel distance, information about the failurelocation, etc.) based on the vehicle ID, and transmits the service clouduser ID and the vehicle information to the service cloud server 40 (stepS33). Incidentally, when the authentication fails, the vehicle cloudserver 30 transmits that to the onboard terminal 20, and the processingends.

The service cloud server 40 performs authentication based on the servicecloud user ID and the vehicle information received from the vehiclecloud server 30 (step S34). Specifically, the service cloud server 40refers to the contract information DB 44, and determines whether or notthe contract corresponding to the service cloud user ID is valid andwhether or not the vehicle information satisfies the condition specifiedin the contract. For example, in case of the service cloud server 40 ofthe insurance company, it is determined whether or not the vehicle thatthe user intends to use satisfies the conditions of the vehiclespecified in the insurance contact of the user. For example, it isassumed that the insurance contract includes a condition that theinsurance service can be applied only when the user is using a vehicleof a specific type. This means that, for example, if the user uses acertain type of vehicle having a high accident rate is used, theinsurance company does not provide the insurance service. In this case,if the user uses a vehicle of a type different from the insurancecontract, the authentication is not successful. Similarly, if theinsurance contract includes such a condition that the insurance serviceis applicable only when the traveling distance of the vehicle used bythe user is within a predetermined range, the authentication is notsuccessful when the user uses the vehicle whose traveling distance islarger than the predetermined distance.

If a contract corresponding to the service cloud user ID exists validlyand the vehicle information satisfies the conditions specified in thecontract, the service cloud server 40 determines that the authenticationis successful. Then, the service cloud server 40 transmits theauthentication result to the vehicle cloud server 30 (step S35).

The vehicle cloud server 30 transmits the authentication result receivedfrom the service cloud server 40 to the onboard terminal 20 (step S36).The onboard terminal 20 notifies the authentication result to the userby the display by the output unit 26 or the like (step S37). Thus, theprocessing ends.

In the second example, since the service cloud server 40 not onlyverifies the service cloud user ID, but also verifies the vehicle thatthe user intends to use with the conditions of the vehicle in the user'scontract to perform the authentication, the service cloud server 40 canappropriately perform the authentication even when there are variouscontract conditions between the user and the service providing company.

In the above embodiment, the vehicle information is described as acondition of providing the insurance service. However, for example, thedriving range of the shared vehicle V (i.e., the area or driving paththe user is going to travel) may be used as a condition of providing theinsurance service. This may be a case of such a contract that theinsurance service is not applied when a user travels in a hazardousarea. In this case, instead of the vehicle information, the servicecloud server 40 receives the information about the user' destination orthe traveling route to the destination from the terminal device 20 viathe vehicle cloud server 30. Then, when a contract corresponding to theservice cloud user ID validly exists and the traveling range of theshared vehicle V satisfies the conditions specified in the contract, theservice cloud server 40 determines that the authentication issuccessful.

[Providing Information from the Vehicle Cloud Server to the ServiceCloud Server]

Next, processing of providing information from the vehicle cloud server30 to the service cloud server 40 will be described. The vehicle cloudserver 30 is operated by an information collection company. The vehiclecloud server 30 regularly acquires various types of information from theonboard terminal 20 of the shared vehicle V, and stores the informationin the history DB 35. On the other hand, while the service cloud server40 does not require all the information that the vehicle cloud server 30acquired from the onboard terminal 20, the server cloud server 40requires specific information to provide the service to the user. Fromthis point of view, the information required for each service cloud isspecified as the provision information, and the service informationincluding the provision information is given to the vehicle cloud server30. The vehicle cloud server 30 provides only the necessary informationto the service cloud server 40 in accordance with the provisioninformation.

In the example of the service information shown in FIG. 5, for example,when an accident occurs to the shared vehicle V, the vehicle cloudserver 30 transmits only the shooting information by the camera for Nminutes before and after the occurrence of the accident among thevarious information acquired from the onboard terminal 20 to the servicecloud server 40 of the insurance company. Also, when the detectionresult of the object acquired by the sensor unit 27 of the sharedvehicle V is different from the map information, the vehicle cloudserver 30 transmits the object recognition information including thatfact and the location information to the service cloud server 40 of themap service company. The service cloud server 40 stores the informationthus received from the vehicle cloud server 30 in the history DB 45.Further, the vehicle cloud server 30 may store the informationtransmitted to the service cloud server 40 in the history DB 35.

FIG. 10 is a flowchart of information providing processing from avehicle cloud server to a service cloud server. As a premise, as shownin step S16 of FIG. 6, the onboard terminal 20 receives and stores theservice information from the user terminal 10.

First, the onboard terminal 20 transmits the service information to thevehicle cloud server 30 (step S41). The vehicle cloud server 30 storesthe received service information in the service information DB 34 (stepS42). Here, it is assumed that the vehicle cloud server 30 performsauthentication based on the shared vehicle user ID received from theonboard terminal 20 in step S22 of FIG. 8, and the onboard terminal 20receives the result indicating that the authentication is successful instep S27 of FIG. 8.

While the shared vehicle V is traveling, the onboard terminal 20transmits various information (hereinafter referred to as “detectioninformation”) acquired by the sensor unit 27 or the like to the vehiclecloud server 30 (step S43). The vehicle cloud server 30 stores thereceived detection information in the history DB 35 (step S44).

Next, the vehicle cloud server 30 refers to the service information, andtransmits the detection information corresponding to the provisioninformation defined for each service cloud among the detectioninformation received from the onboard terminal 20 to the service cloudserver 40. For example, in the example of FIG. 5, the vehicle cloudserver 30 of the vehicle cloud CL001 transmits the shooting informationfor N minutes before and after the occurrence of the accident to theservice cloud server 40 of the insurance company (i.e., to thedestination address “xxx.xxx.co.jp”). The service cloud server 40 storesthe received detection information in the history DB 45.

Thus, by providing the vehicle cloud server 30 with the serviceinformation including the provision information, the vehicle cloudserver 30 can efficiently transmit only the information required by theservice providing company among the various detection informationacquired by the onboard terminal 20 to the service cloud server 40.

When the vehicle cloud server 30 transmits the detection informationcorresponding to the provision information to the service cloud server40, it is preferred that the vehicle cloud server 30 stores the historyinformation indicating the detection information that the vehicle cloudserver 30 transmitted to the service cloud server 40 in the history DB35.

[Use End Processing]

Next, processing for ending the use of the shared vehicle V by the userwill be described. FIG. 11 is a flowchart of the use end processingexecuted when the user ends the use of the shared vehicle V. When theuser enters a use ending instruction into the user terminal 10, the userterminal 10 transmits a use end request to the onboard terminal 20 (StepS50). For example, while the user is using the shared vehicle V, theuser terminal 10 may display a button for instructing the end of use(e.g., a “get off” button) or the like, and when the user presses thebutton, the user terminal 10 may determine that the instruction to endthe use has been input.

Upon receiving the use end request from the user terminal 10, theonboard terminal 20 transmits the use end request to the vehicle cloudserver 30 (step S51). Upon receiving the use end request, the vehiclecloud server 30 performs the use end processing (step S52).Specifically, the vehicle cloud server 30 cancels registration of theuser as the user of the shared vehicle V, and terminates transmission ofthe detection information to the service cloud server 40. The vehiclecloud server 30 notifies the service cloud server 40 of the end of theuse by the user (step S53). Thus, the service cloud server 40 recognizesthat the use of the shared vehicle V by the user has been ended and thatthe transmission of the detection information from the vehicle cloudserver 30 is stopped.

Further, the vehicle cloud server 30 transmits a notification of useending indicating that the use end processing has been performed to theonboard terminal 20 (step S54). Upon receiving the notification of theuse ending from the vehicle cloud server 30, the onboard terminal 20transmits the notification of the use ending to the user terminal 10(step S55). The user terminal 10 displays the end of use on the displayunit 14 (step S56), and notifies the user that the use by the user hasbeen correctly ended.

[History Deletion Process]

Next, processing of deleting the history information stored in thevehicle cloud server 30 and the service cloud server 40 will bedescribed. As described above, the vehicle cloud server 30 stores theinformation acquired from the onboard terminal 20 in the history DB 35while the user uses the shared vehicle V. Further, the service cloudserver 40 receives the detection information corresponding to theprovision information from the vehicle cloud server 30 during use of theshared vehicle V by the user, and stores the detection information inthe history DB 45. Since these provision information is personalinformation for the user, some users does not want the provisioninformation to be kept recorded in the information collection company orthe service providing company even after the provision of the servicefrom the service providing company is ended. Therefore, the user canrequest the deletion of these history information after ending the useof the shared vehicle V. The vehicle cloud server 30 and the servicecloud server 40 delete the history information based on the deletionrequest by the user.

FIG. 12 is a flowchart of history deletion processing. First, the useroperates the user terminal 10 to transmit a history deletion request tothe onboard terminal 20 (step S60). The history deletion requestincludes the shared vehicle user ID of the user. When receiving thehistory deletion request from the user terminal 10, the onboard terminal20 transmits the history deletion request to the vehicle cloud server 30(step S61).

When receiving the history deletion request, the vehicle cloud server 30deletes the history information corresponding to the shared vehicle userID included in the history deletion request among the historyinformation stored in the history DB 35 (step S62). Further, the vehiclecloud server 30 transmits the history deletion request to the servicecloud server 40 (step S63). At that time, the vehicle cloud server 30refers to the service information, and transmits the history deletionrequest including the service cloud user ID to the service cloud server40.

When receiving the history deletion request, the service cloud server 40deletes the history information corresponding to the service cloud userID included in the history deletion request among the historyinformation stored in the history DB 45 (step 64). The service cloudserver 40 transmits a notification of completion of deletion indicatingthat the history information has been deleted to the vehicle cloudserver 30 (step S65).

When receiving the notification of completion of deletion from theservice cloud server 40, the vehicle cloud server 30 transmits thenotification of completion of deletion to the onboard terminal 20 (stepS66). This notification indicates that both 6 the deletion of thehistory in the vehicle cloud server 30 and the deletion of the historyin the service cloud server 40 have been completed.

Upon receiving the notification of completion of deletion from thevehicle cloud server 30, the onboard terminal 20 transfers thenotification of completion of deletion to the user terminal 10 (stepS67). Upon receiving the notification of the deletion completion fromthe onboard terminal 20, the user terminal 10 performs a displayindicating that the deletion has been completed on the display unit 14(step S68). This allows the user to know 16 that the history informationhas been deleted correctly.

In the above example, the history deletion request by the user istransmitted to the vehicle cloud server 30 through the onboard terminal20. Instead, the history deletion request may be transmitted directlyfrom the user terminal 10 to the vehicle cloud server 30. In addition,the history deletion request may include a range of information to bedeleted, for example, the date and time when the information wastransmitted. In this case, the vehicle cloud server 30 and the servicecloud server 40 delete the history information corresponding to thespecified date and time. Also, when the information about the amount ofinformation transmitted to the service cloud server 40 (e.g., the amountof data, the number of record, etc.) is stored for each service clouduser ID, the vehicle cloud server 30 may receive the information aboutthe amount of the information deleted by the service cloud server 40together with the notification of the completion of deletion from theservice cloud server 40. In this case, the vehicle cloud server 30 canverify that the history information has been deleted certainly, andtransmit the notification of the completion of deletion to the onboardterminal 20.

[Utilization of Biometric Authentication]

Next, description will be given of a method of utilizing biometricinformation in the authentication of users using the shared vehicle V.When the users use the vehicle cloud or the service cloud, it isnecessary to prevent spoofing. An example of spoofing is that, after auser X completes the authentication for the vehicle cloud and theservice cloud, another user Y uses the shared vehicle V. If thishappens, the service providing company needs to provide services to theuser Y who has not made the contract, based on the contract with theuser X. Therefore, the authentication using biometric information iscarried out at the time of starting the use and during the actual use ofthe shared vehicle V.

FIG. 13 schematically illustrates a method of authentication usingbiometric information. In the following example, fingerprint informationshall be used as biometric information. First, at the time ofauthentication for starting use, fingerprint authentication is performedby the user terminal 10. When authentication is successful, the userterminal 10 transmits the fingerprint information to the onboardterminal 20. The onboard terminal 20 stores the received fingerprintinformation in the storage unit 22 or the like. Then, as describedabove, authentication for starting use is performed by the vehicle cloudserver 30 and the service cloud server 40.

Thereafter, while the user is using the shared vehicle V, the onboardterminal 20 periodically performs biometric authentication by utilizingthe steering or the like of the shared vehicle V. For example, a sensorprovided on the steering of the shared vehicle V detects the fingerprintinformation of the user. The onboard terminal 20 verifies thefingerprint information obtained from the user terminal 10 at the timeof starting the use with the biometric information obtained from thesensor during use of the shared vehicle V. If those biometricinformation coincides, the identity of the user who made theauthentication the time of starting the use and the user who is actuallyusing the shared vehicle V is guaranteed. Therefore, the onboardterminal 20 notifies the vehicle cloud server 30 that the user who hasmade the authentication at the time of starting the use and the user whois using the shared vehicle V are matched. Also, the vehicle cloudserver 30 also notifies the service cloud server 40 that a legitimateuser is using the shared vehicle V. In this way, spoofing can bedetected. In the above example, the fingerprint information is used asthe biometric information. However, other biometric information may beused, or a face authentication or the like may be used.

FIG. 14 is a flowchart illustrating authenticating process at the timeof starting the use using biometric information. The user performsbiometric authentication such as fingerprint 16 authentication using theuser terminal 10 (step S60). When the authentication is successful, theuser terminal 10 transmits the biometric information to the onboardterminal 20 (step S61). The onboard terminal 20 stores the biometricinformation transmitted from the user terminal 10 (step S62), andtransmits an authentication request to the vehicle cloud server 30 (stepS63). At this time, as described above, the onboard terminal 20transmits the shared vehicle user ID and the service cloud user ID tothe vehicle cloud server 30.

The vehicle cloud server 30 performs authentication based on the sharedvehicle user ID (step S64). When the authentication is successful, thevehicle cloud server 30 transmits an authentication request includingthe service cloud user ID to the service cloud server 40 (step S65). Theservice cloud server 40 performs authentication based on the servicecloud user ID (step S66), and transmits the authentication result to thevehicle cloud server 30 (step S67).

The vehicle cloud server 30 transmits the authentication result receivedfrom the service cloud server 40 to the onboard terminal 20 (step S68),and the onboard terminal 20 transmits the authentication result receivedfrom the vehicle cloud server 30 to the user terminal 10 (step S69). Theuser terminal 10 displays the received authentication result on thedisplay unit 14 (step S70). In this way, the authentication process atthe time of starting the use is completed.

FIG. 15 is a flowchart of the authentication processing during the useof the shared vehicle V by the user. The onboard terminal 20periodically detects the biometric information of the user by a sensoror the like (step S71), and verifies it with the biometric informationacquired from the user terminal 10 at the time of starting the use.Then, the onboard terminal 20 transmits the verification result to thevehicle cloud server 30 (step S73). The vehicle cloud server 30transmits the received verification result to the service cloud server40 (step S74). Thus, when the biometric information matches in step S72,the vehicle cloud server 30 and the service cloud server 40 are notifiedthat a valid user is using the shared vehicle V. On the other hand, whenthe biometric information does not match in step S72, the verificationresult indicating that fact is transmitted to the vehicle cloud server30 and the service cloud server 40, so that the vehicle cloud and theservice cloud can appropriately respond.

BRIEF DESCRIPTION OF REFERENCE NUMBERS

-   -   10 User terminal    -   20 Onboard terminals    -   27 Sensor unit    -   30 Vehicle cloud server    -   40 Service cloud server

1. A server device which collects information from a vehicle,comprising: a storage unit configured to receive acquired informationacquired by the vehicle from an onboard terminal mounted on the vehicleduring a use of the vehicle b a user, and stores the acquiredinformation; an information providing unit configured to provideinformation requested by a service providing company which provides aservice related to the vehicle, among the required information, to aserver device of the service providing company; a reception unitconfigured to receive a deletion request of the acquired information; adeletion unit configured to delete the acquired information stored inthe storage unit; and a transmission unit configured to transmit adeletion request of the acquired information provided to the serviceproviding company to the server device of the service providing companybased on the deletion request.
 2. The server device according to claim1, wherein the storage unit stores information requested by the serviceproviding company for each service providing company.
 3. The servicedevice according to claim 1, wherein the reception unit receives thedeletion request from the onboard terminal.
 4. The server deviceaccording to claim 1, wherein the reception unit receives the deletionrequest from a terminal device of the user.
 5. The server deviceaccording to claim 1, further comprising a notification unit configuredto receive a notification indicating that the acquired information isdeleted from the server device of the service providing company, andnotifies the onboard terminal that the acquired information is deletedfrom the server device of the service providing company.
 6. The serverdevice according to claim 5, wherein the notification unit compares anamount of the acquired information provided to the service providingcompany with the amount of the acquired information deleted by theservice providing company to confirm that the acquired information isdeleted, and notifies the onboard terminal that the acquired informationis deleted from the server device of the service providing company whenit is confirmed that the acquired information is deleted.
 7. The serverdevice according to claim 5, wherein the notification unit notifies theonboard terminal that the acquired information is deleted from thestorage unit by the deletion unit.
 8. An information processing methodexecuted by a server device which collects information from a vehicle,comprising: a storage process configured to receive acquired informationacquired by the vehicle from an onboard terminal mounted on the vehicleduring a use of the vehicle by a user, and stores the acquiredinformation in a storage unit; an information providing processconfigured to provide information requested by a service providingcompany which provides a service related to the vehicle, among therequired information, to a server device of the service providingcompany; a reception process configured to receive a deletion request ofthe acquired information; a deletion process configured to delete theacquired information stored in the storage unit; and a transmissionprocess configured to transmit a deletion request of the acquiredinformation provided to the service providing company to the serverdevice of the service providing company based on the deletion request.9. A non-transitory computer-readable medium storing a program executedby a server device which includes a computer and which collectsinformation from a vehicle, the program causing the computer to functionas; a storage unit configured to receive acquired information acquiredby the vehicle from an onboard terminal mounted on the vehicle during ause of the vehicle by a user, and stores the acquired information; aninformation providing unit configured to provide information requestedby a service providing company which provides a service related to thevehicle, among the required information, to a server device of theservice providing company; a reception unit configured to receive adeletion request of the acquired information; a deletion unit configuredto delete the acquired information stored in the storage unit; and atransmission unit configured to transmit a deletion request of theacquired information provided to the service providing company to theserver device of the service providing company based on the deletionrequest.
 10. (canceled)